| 翻訳と辞書 |
| Polyglot Persistence ： ウィキペディア英語版 |
Polyglot Persistence
In 2006, Neal Ford coined the term polyglot programming, to express the idea that applications should be written in a mix of languages to take advantage of the fact that different languages are suitable for tackling different problems. Complex applications combine different types of problems, so picking the right language for each job may be more productive than trying to fit all aspects into a single language.
There are numerous databases out there which solves different problems. Having a single database to solve all of the requirements results in non-performant solution. For example, data relationships. RDBMS solutions are good at enforcing that relationships exist. To discover a relationship or to find data from different tables that belong to the same object, we can make use of SQL join. This might work when the data is less. The problem starts when the data grows bigger. Graph databases might solve the problem of relationship in case of BigData but it might solve the problem of transactions which is provided by RDBMS. So, we have two different problems here which is solved by two different databases. Polyglot persistence is to use different data storage technologies to handling varying data storage needs.
抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』
■ウィキペディアで「Polyglot Persistence」の詳細全文を読む
スポンサード リンク
| 翻訳と辞書 : 翻訳のためのインターネットリソース |
Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.
|
|